- 
                Notifications
    You must be signed in to change notification settings 
- Fork 796
Use Nginx config with outlets #913
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
a8e3a89    to
    8250508      
    Compare
  
    8250508    to
    135aab5      
    Compare
  
    ca741a9    to
    12299cc      
    Compare
  
    12299cc    to
    e216fa7      
    Compare
  
    | The nginx config used in the  As an outsider who has to maintain some custom pups for adding extra IPv6 and SSL support, the "outlets" seems like a reasonable way to clean things up. Nice work @nbianca 👍 1 minor suggestion: The since nginx includes are included in alphabetical order, it may then make sense to prefix numerically to enforce order eg:  | 
This config has several 'include' statements that serve as extension outlets. Most of the "find & replace" instructions from templates files have been replaced to use outlets. This commit also deprecates IPv6 template in favour of an automatic implementation that relies on container's connectivity.
| Since the  | 
This reverts commit 7b042d6. `web.socketed.template.yml` is broken
This config has several 'include' statements that serve as extension
outlets. Most of the "find & replace" instructions from templates
files have been replaced to use outlets.
This commit also deprecates IPv6 template in favour of an automatic
implementation that relies on container's connectivity.